fix(evolution): unblock analysis/implementation/integration by accepting GITHUB_TOKEN over GITHUB_PRIVATE_TOKEN#470
Merged
Lexus2016 merged 1 commit intoJun 23, 2026
Conversation
… accepting GITHUB_TOKEN instead of requiring GITHUB_PRIVATE_TOKEN The evolution analysis, implementation, and integration cron jobs were configured to require GITHUB_PRIVATE_TOKEN, which is not set in the cron environment. However, GITHUB_TOKEN IS set and the gh CLI is already authenticated via persistent gh auth login. Changes: - Switch token_env from GITHUB_PRIVATE_TOKEN to GITHUB_TOKEN in all three cron yaml configs - Update prompt instructions to verify gh CLI auth first, falling back to GITHUB_TOKEN - Update all three SKILL.md files (security sections, operating mode, frontmatter mode field, description) - Change mode from PRIVATE to PUBLIC since the auth mechanism is now the standard GITHUB_TOKEN / gh CLI path Co-Authored-By: Hermes Evolution <evolution@hermes.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[evolution]
Summary
Fixes the evolution analysis/implementation/integration pipeline that has been blocked for 8+ days.
Problem
All three PRIVATE-mode evolution stages (analysis at 21:00, implementation at 22:00, integration at 23:00) required
GITHUB_PRIVATE_TOKENwhich is not set in the cron environment. This caused the analysis stage to immediately abort with "GITHUB_PRIVATE_TOKEN is not set. Aborting" or fail with a broken pipe error — blocking the entire pipeline.Meanwhile,
GITHUB_TOKENIS set and theghCLI is already authenticated via persistentgh auth login(~/.config/gh) with all required scopes.Changes
cron/evolution/{analysis,implementation,integration}.yaml
token_envfromGITHUB_PRIVATE_TOKENtoGITHUB_TOKENgh auth statusfirst, then fall back toGITHUB_TOKENskills/evolution/evolution-{analysis,implementation,integration}/SKILL.md
modefrom PRIVATE to PUBLICgh auth statusinstead of requiringGITHUB_PRIVATE_TOKENImpact
Unblocks the entire evolution pipeline so daily analysis → implementation → integration can run successfully.